At Flipt we’ve recently undergone a journey to create a GitOps experience for feature flags. We’ve created a way to put feature flags in Git in our open source solution. But we’re not done with GitOps just yet. As we built capabilities for our feature flag solution to read flag state from Git, we recognized that the GitOps solution space has a wealth of answers for reading state from Git, however, there seems to be a lack of tooling built around the experience of producing and contributing changes to GitOps repositories. In previous roles working on GitOps pipelines, we found ourselves building tools to expose state through more meaningful APIs and creating automation to generate pull requests for common configuration changes. So we asked ourselves how could we make this task easier? In this talk, I will take you on the journey we’ve been on to put feature flags in Git, define the new problems we’ve unearthed along the way and reflect on past experiences filling in the GitOps gaps, and present then our new open source project Cup, an extensible API server for your Git. Then explore some of the things we think you could build on top of it.